At 12:49 PM -0500 7/21/03, Bruno Wolff III wrote:
>If you just need uniqueness (e.g. there can be gaps in the ids), you
>can use sequences to do this more efficiently.
Thanks for the [three] speedy replies!
I know my example was simple--I just wanted to illustrate.
I want to put as much of the code as possible in the database front
end for control and maintenance purposes. I have explicitly
considered the performance degradation and am willing to accept it.
Although having written this, maybe I should just lock everything in
"access exclusive mode" for the brief periods of time these
transactions will be pending, and not worry about identifying the
_least_ restrictive that will block intercurrent Selects (until I
actually do create a performance problem).
[After writing the paragraph immediately above I received Stephan
Szabo's response, which perhaps endorses draconian locks given my
perception of my need.]
AB
